Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices

ABSTRACT

Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices. The systems and methods employ at least one decentralized revision control system as a data repository for storing data, such as configuration data, and at least one data provisioning component as an interface for accessing the configuration data stored in the data repository. By employing the decentralized revision control system in conjunction with the data provisioning component, the systems and methods can provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of the configuration data.

CROSS REFERENCE TO RELATED APPLICATIONS

Not applicable

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable

FIELD OF THE INVENTION

The present application relates generally to telecommunications systems and devices, and more specifically to systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices.

BACKGROUND OF THE INVENTION

Telecommunications systems and devices, such as access systems, network management systems, media switching centers, cross-connects, session border controllers, etc., can be adapted via configuration data to provide specific functionality for a target application. Based on such configuration data, control software within the telecommunications systems and devices can control the respective systems and devices to satisfy the requirements of the target application. For example, such configuration data can be specified for a session border controller to satisfy the requirements of access and interconnect applications within mobile and/or fixed voice-over-Internet protocol (such voice-over-Internet protocol is also referred to herein as “VoIP”) networks. By adapting the session border controller using such configuration data, the session border controller can be effectively controlled to provide security for the interconnect and access network infrastructure, thereby assuring that VoIP services are made continuously available while maintaining a high level of system performance.

In typical telecommunications systems and devices, large amounts of complex configuration data must generally be stored and managed. Further, within a typical target application, such configuration data generally has to be accessed in a controlled manner, and the history of any changes made to the configuration data has to be tracked and maintained. Moreover, users of such telecommunications systems and devices generally require the capabilities of rolling back such changes to the configuration data, as required and/or as desired, and successfully synchronizing the configuration data across other telecommunications systems and/or devices over a network. However, prior attempts to provide such functionality in telecommunications systems and devices have generally not been suited for use in real-time applications that require fast, dynamic access to configuration data.

It would therefore be desirable to have improved systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices that better address the issues relating to the storage and management of data, such as configuration data, in real-time applications.

BRIEF SUMMARY OF THE INVENTION

In accordance with the present application, improved systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices are disclosed. The presently disclosed systems and methods employ at least one decentralized revision control system as a data repository for storing data, such as configuration data, and at least one data provisioning component as an interface for accessing the configuration data stored in the data repository. By employing the decentralized revision control system in conjunction with the data provisioning component, the presently disclosed systems and methods can beneficially provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of the configuration data.

In accordance with a first aspect, an exemplary system for provisioning data storage and runtime configuration in telecommunications systems and devices (such an exemplary system is also referred to herein as a/the “data provisioning and runtime configuration system”) includes the decentralized revision control system, and one or more functional components including at least the data provisioning component. For example, the decentralized revision control system can be implemented using the Git revision control system, or any other suitable decentralized revision control system. The functional components can further include a view manager component, as well as one or more predetermined application program components in support of the functionality provided by the data provisioning and runtime configuration system. In accordance with a first exemplary aspect, a user can access the data provisioning and runtime configuration system over a network via any suitable client, including, but not limited to, a web client, which is communicably coupleable to the view manager component via a network connection. The view manager component can be implemented as any suitable server interface, including, but not limited to, a web server interface, for providing an overall view of the current state of the system configuration. Using the web client, the user can access the view manager component over the network via a web browser, which is communicably coupleable to the web server interface of the view manager component via the network connection. The view manager component is communicably coupled to the data provisioning component, which, in turn, is communicably coupled to the decentralized revision control system. In further accordance with the first exemplary aspect, data, such as configuration data, including but not limited to real-time data, can be stored in the data repository of the decentralized revision control system as objects (such objects are also referred to herein as “data objects”). Using the web browser, the user can communicate with the view manager component over the network connection to request access to, additions to, updates to, and/or deletions of specific data objects stored in the data repository. The view manager component is operative to communicate with the data provisioning component to implement such access to, additions to, updates to, and/or deletions of such data objects, as requested by the user. In accordance with a second exemplary aspect, the data provisioning component is operative to send commands, e.g., system calls, to the data repository over a source code management (SCM) interface of the decentralized revision control system, thereby implementing the requested access to, additions to, updates to, and/or deletions of such data objects stored in the data repository. In further accordance with the second exemplary aspect, the user can communicate with the data provisioning component to subscribe, via at least one subscription message, to specific data objects stored in the data repository, e.g., for the purpose of being notified whenever certain characteristics of such data objects change, as determined by the data provisioning component. In the event the data provisioning component determines that such certain characteristics of the data objects have, in fact, changed, the data provisioning component can notify the subscribing user of the change(s). In accordance with a third exemplary aspect, one or more of the predetermined application program components can register, with the data provisioning component, one or more application entities that may require access to the data objects stored in the data repository. The registered application entities are each operative to communicate with the data provisioning component to request access to specific data objects stored in the data repository. Further, the data provisioning component is operative to implement such access to such data objects, as requested by the respective application entities. The registered application entities are each further operative to communicate with the data provisioning component to subscribe to specific data objects, e.g., for the purpose of being notified whenever certain characteristics of such data objects change, as determined by the data provisioning component. In the event the data provisioning component determines that such certain characteristics of the data objects have, in fact, changed, the data provisioning component notifies the respective application entities, as appropriate.

In accordance with a second aspect, two or more data provisioning and runtime configuration systems can be implemented as peer systems. Each of the peer systems can include a respective decentralized revision control system, and a respective data provisioning component. Each of the peer systems can further include a view manager component, as well as one or more predetermined application program components. The decentralized revision control systems, the data provisioning components, the view manager component(s), and the predetermined application program component(s) included in the respective peer systems are each configured to operate as described above with reference to the first aspect of the data provisioning and runtime configuration system. The data provisioning components included in the respective peer systems are further operative to communicate with one another over at least one messaging interface via a first network connection. Moreover, the decentralized revision control systems included in the respective peer systems are further operative to communicate with one another via a second network connection, in accordance with a predetermined version control communication protocol. In the event one of the data provisioning components included in the respective peer systems determines that certain characteristics of specific data objects stored in the data repository of the decentralized revision control system coupled thereto have changed, the data provisioning component can send, over the messaging interface via the first network connection, a notification of the changes to the data provisioning component included in the other peer system. Further, the data provisioning components included in the peer systems can send commands, e.g., system calls, to the respective decentralized revision control systems coupled thereto, thereby causing the respective decentralized revision control systems to synchronize the changes to the data objects stored therein via the second network connection, in accordance with the predetermined version control communication protocol.

By employing the decentralized revision control system in conjunction with the data provisioning component, the data provisioning and runtime configuration system can beneficially provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of data, such as configuration data, including but not limited to real-time data. Further, by implementing two or more such data provisioning and runtime configuration systems as peer systems, any changes to the data objects stored in the data repositories of the respective peer systems can be beneficially synchronized using a predetermined version control communication protocol, thereby assuring that none of the data are lost in the event of a failover.

Other features, functions, and aspects of the invention will be evident from the Drawings and/or the Detailed Description of the Invention that follow.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The invention will be more fully understood with reference to the following Detailed Description of the Invention in conjunction with the drawings of which:

FIG. 1 is a block diagram of an exemplary architecture for provisioning data storage and runtime configuration in telecommunications systems and devices, in accordance with an exemplary embodiment of the present application; and

FIG. 2 is a flow diagram of an exemplary method of operating an exemplary data provisioning and runtime configuration system within the exemplary architecture of FIG. 1.

DETAILED DESCRIPTION OF THE INVENTION

Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices are disclosed. The presently disclosed systems and methods employ at least one decentralized revision control system as a data repository for storing data, such as configuration data, and at least one data provisioning component as an interface for accessing the configuration data stored in the data repository. By employing the decentralized revision control system in conjunction with the data provisioning component, the presently disclosed systems and methods can beneficially provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of the configuration data.

FIG. 1 depicts an illustrative embodiment of an exemplary architecture 100 for provisioning data storage and runtime configuration in telecommunications systems and devices, in accordance with an exemplary embodiment of the present application. The exemplary architecture 100 includes a plurality of telecommunications systems or devices 102, 104 (such telecommunications systems or devices are also referred to herein as “telecommunications platforms”). Telecommunications platforms 102, 104 can be implemented as access systems, network management systems, media switching centers, cross-connects, session border controllers, as examples, and/or as any other suitable telecommunications systems or devices.

In accordance with the illustrative embodiment of FIG. 1, telecommunications platform 102 includes a data provisioning and runtime configuration system 101 a, and telecommunications platform 104 includes a data provisioning and runtime configuration system 101 b. Each of the data provisioning and runtime configuration systems 101 a, 101 b includes a decentralized revision control system, and one or more functional components including at least a data provisioning component. Specifically, the data provisioning and runtime configuration system 101 a includes a decentralized revision control system 112 and a data provisioning component 116. Similarly, the data provisioning and runtime configuration system 101 b includes a decentralized revision control system 114 and a data provisioning component 118. With reference to telecommunications platform 104, the functional components within the data provisioning and runtime configuration system 101 b further include a view manager component 120. Moreover, with reference to telecommunications platform 102, the functional components within the data provisioning and runtime configuration system 101 a further include one or more predetermined application program components 108, 110 in support of the functionality provided by telecommunications platform 102.

It is noted that the functional components within the data provisioning and runtime configuration system 101 b can further include one or more predetermined application program components 111, 113 in support of the functionality provided by telecommunications platform 104.

As shown in FIG. 1, one or more user clients, such as a user client 106, can access the data provisioning and runtime configuration system 101 b within telecommunications platform 104 over a network. The user client 106 can be implemented as a web client, as an example, or as any other suitable client communicably coupleable to the view manager component 120 via a network connection 136. Moreover, the view manager component 120 can be implemented as any suitable server interface, including, but not limited to, a web server interface, for providing an overall view of the current state of the system configuration. For example, the user client 106 implemented as a web client can access the data provisioning and runtime configuration system 101 b over the network via a web browser communicably coupled to the web server interface of the view manager component 120. The view manager component 120 is communicably connected to the data provisioning component 118, which, in turn, is communicably connected to the decentralized revision control system 114. In further accordance with the illustrative embodiment of FIG. 1, data, such as configuration data, including but not limited to real-time data, can be stored in a data repository of the decentralized revision control system 114 as objects (such objects are also referred to herein as “data objects”). For example, the decentralized revision control systems 112, 114 can each be implemented using any suitable decentralized revision control system, such as the Git revision control system that provides at least one data repository with at least history and revision capabilities and is not dependent on network access and/or on a central server.

In accordance with an exemplary mode of operation of the data provisioning and runtime configuration system 101 b within telecommunications platform 104, the user client 106 communicates, using the web browser, with the view manager component 120 over the network connection 136 to request access to, and/or one or more manipulations of, specific data objects stored in the data repository of the decentralized revision control system 114. For example, such manipulations of data objects can include one or more additions to, updates to, and/or deletions of the respective data objects. Further, the user client 106 can communicate with the view manager component 120 over the network connection 136 using the hypertext transfer protocol (HTTP), or any other suitable communications protocol. The view manager component 120 is operative to communicate with the data provisioning component 118 over a connection 134 to implement such access to, additions to, updates to, and/or deletions of the specific data objects contained in the decentralized revision control system 114, as requested by the user client 106. Moreover, the data provisioning component 118 is operative to send commands, e.g., system calls, to the decentralized revision control system 114 over an interface 132 of the decentralized revision control system 114, thereby implementing the requested access to, additions to, updates to, and/or deletions of the specific data objects stored in the data repository of the decentralized revision control system 114. For example, the interface 132 can be implemented as a source code management (SCM) interface of the decentralized revision control system 114, or any other suitable interface. In further accordance with this exemplary mode of operation of the data provisioning and runtime configuration system 101 b, the user client 106 can communicate with the data provisioning component 118 to subscribe, via at least one subscription message, to the specific data objects stored in the data repository of the decentralized revision control system 114. For example, the user client 106 can subscribe to the specific data objects for the purpose of being notified whenever certain characteristics of such data objects change, as determined by the data provisioning component 118. In the event the data provisioning component 118 determines that such certain characteristics of the data objects have, in fact, changed, the data provisioning component 118 generates and sends at least one notification of the changes to the view manager component 120 over the connection 134, and the view manager component 120, in turn, notifies the user client 106 of the changes over the network connection 136, for example, via the web browser. In accordance with an exemplary mode of operation of the data provisioning and runtime configuration system 101 a within telecommunications platform 102, each of the predetermined application program components 108, 110 can register, with the data provisioning component 116, one or more application entities that may require access to the data objects stored in the data repository of the decentralized revision control system 112. For example, the predetermined application program components 108, 110 can each register one or more application entities. The application entities registered by the application program components 108, 110 are operative to communicate with the data provisioning component 116 over connections 122, 124, respectively, to request access to, additions to, updates to, and/or deletions of specific data objects stored in the data repository of the decentralized revision control system 112. Further, the data provisioning component 116 is operative to implement such access to, additions to, updates to, and/or deletions of such data objects, as requested, on behalf of the respective application entities. The registered application entities are each further operative to communicate with the data provisioning component 116 to subscribe to specific data objects stored in the data repository of the decentralized revision control system 112. For example, each registered application entity can subscribe to the specific data objects for the purpose of being notified whenever certain characteristics of such data objects change, as determined by the data provisioning component 116. In the event the data provisioning component 116 determines that such certain characteristics of the data objects have, in fact, changed, the data provisioning component 116 can notify the respective application entities over the connections 122, 124, as appropriate.

In further accordance with the illustrative embodiment of FIG. 1, the data provisioning and runtime configuration system 101 a within telecommunications platform 102, and the data provisioning and runtime configuration system 101 b within telecommunications platform 104, can be implemented as peer systems. In such an implementation of the data provisioning and runtime configuration systems 101 a, 101 b, the data provisioning components 116, 118 included in the respective systems 101 a, 10 lb are operative to communicate with one another over a messaging interface 128. Moreover, the decentralized revision control systems 112, 114 included in the respective systems 102, 104 are operative to communicate with one another via a network connection 130, in accordance with a predetermined version control communication protocol, such as HTTP, UUCP, FTP, SMTP, NNTP, or any other suitable communications protocol.

In accordance with an exemplary mode of operation of the data provisioning and runtime configuration systems 101 a, 101 b implemented as peer systems, in the event the data provisioning component 118 included in the data provisioning and runtime configuration system 101 b determines that certain characteristics of data objects stored in the data repository of the decentralized revision control system 114 coupled thereto have changed, the data provisioning component 118 sends, over the messaging interface 128, a notification of the changes to the data provisioning component 116. Further, the data provisioning components 116, 118 send commands, e.g., system calls, to the decentralized revision control systems 112, 114, respectively, thereby causing the decentralized revision control systems 112, 114 to synchronize the changes to the data objects stored therein via the network connection 130, in accordance with the predetermined version control communication protocol. For example, each of the data repositories of the respective decentralized revision control systems 112, 114 may contain configuration data. Further, the data repository of one of the decentralized revision control systems 112, 114 may contain at least a portion of the configuration data stored in the other one of the decentralized revision control systems 112, 114. Moreover, each of the decentralized revision control systems 112, 114 can synchronize the changes to the configuration data in the data objects stored therein by fetching such changes to the data objects over the network connection 130, using HTTP or any other suitable communications protocol, In addition, the data provisioning component 116 can notify the registered application entities of the changes to the data objects over the connections 122, 124, as appropriate. By implementing the data provisioning and runtime configuration systems 101 a, 101 b as peer systems, a high availability deployment can be achieved that assures that none of the data stored in the data repositories of the decentralized revision control systems 112, 114 are lost in the event of a failover.

An exemplary method of operating a data provisioning and runtime configuration system within the architecture 100 is described below with reference to FIG. 2, as well as FIG. 1. As depicted in step 202 (see FIG. 2), at least one request for access to, or manipulation of, data stored in the data repository of the decentralized revision control system 114 (see FIG. 1) is received at the data provisioning component 118 (see FIG. 1) within telecommunications platform 104 (see FIG. 1). As depicted in step 204 (see FIG. 2), one or more commands are sent, by the data provisioning component 118 (see FIG. 1), to the decentralized revision control system 114 (see FIG. 1) to implement the requested access to, or manipulation of, the data stored in the data repository of the decentralized revision control system 114 (see FIG. 1). As depicted in step 206 (see FIG. 2), in the event at least a portion of the data stored in the data repository of the decentralized revision control system 114 (see FIG. 1) has changed due to the requested access to, or manipulation of, the data, a notification of the changes is sent, by the data provisioning component 118 (see FIG. 1) over the messaging interface 128 (see FIG. 1), to the data provisioning component 116 (see FIG. 1) within telecommunications platform 102 (see FIG. 1). As depicted in step 208 (see FIG. 2), one or more commands are sent, by the data provisioning components 116, 118 (see FIG. 1), to the respective decentralized revision control systems 112, 114 (see FIG. 1) connected thereto, causing the decentralized revision control systems 112, 114 (see FIG. 1) to synchronize the changes to the data objects stored therein via the network connection 130 (see FIG. 1).

It is noted that the operations depicted and/or described herein are purely exemplary, and imply no particular order. Further, the operations can be used in any sequence, when appropriate, and/or can be partially used. With the above illustrative embodiments in mind, it should be understood that such illustrative embodiments can employ various computer-implemented operations involving data transferred or stored in computer systems. Such operations are those requiring physical manipulation of physical quantities. Typically, though not necessarily, such quantities take the form of electrical, magnetic, and/or optical signals capable of being stored, transferred, combined, compared, and/or otherwise manipulated.

Further, any of the operations depicted and/or described herein that form part of the illustrative embodiments are useful machine operations. The illustrative embodiments also relate to a device or an apparatus for performing such operations. The apparatus can be specially constructed for the required purpose, or can be a general-purpose computer selectively activated or configured by a computer program stored in the computer. In particular, various general-purpose machines employing one or more processors coupled to one or more computer readable media can be used with computer programs written in accordance with the teachings disclosed herein, or it may be more convenient to construct a more specialized apparatus to perform the required operations.

The presently disclosed systems and methods can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data, which can thereafter be read by a computer system. Examples of such computer readable media include hard drives, read-only memory (ROM), random-access memory (RAM), CD-ROMs, CD-Rs, CD-RWs, magnetic tapes, and/or any other suitable optical or non-optical data storage devices. The computer readable media can also be distributed over a network-coupled computer system, so that the computer readable code can be stored and/or executed in a distributed fashion.

The foregoing description has been directed to particular illustrative embodiments of this disclosure. It will be apparent, however, that other variations and modifications may be made to the described embodiments, with the attainment of some or all of their associated advantages. Moreover, the procedures, processes, and/or modules described herein may be implemented in hardware, software, embodied as a computer-readable medium having program instructions, firmware, or a combination thereof. For example, the functions described herein may be performed by a processor executing program instructions out of a memory or other storage device.

It will be appreciated by those skilled in the art that modifications to and variations of the above-described systems and methods may be made without departing from the inventive concepts disclosed herein. Accordingly, the disclosure should not be viewed as limited except as by the scope and spirit of the appended claims. 

What is claimed is:
 1. A system for provisioning data storage and runtime configuration in a telecommunications system or device, comprising: a decentralized revision control system including a data repository, the data repository being operative to store at least configuration data for the telecommunications system or device; and a data provisioning component communicably connected to the decentralized revision control system, wherein the data provisioning component is operative: to receive at least one request for access to, or manipulation of, the configuration data stored in the data repository of the decentralized revision control system; and to send at least one command to the decentralized revision control system to implement the requested access to, or manipulation of, the configuration data stored in the data repository of the decentralized revision control system.
 2. The system of claim 1 wherein the decentralized revision control system has a source code management (SCM) interface, and the data provisioning component is further operative to send the at least one command to the decentralized revision control system over the SCM interface.
 3. The system of claim 1 wherein the configuration data in the data repository of the decentralized revision control system are stored as one or more data objects, and wherein the data provisioning component is further operative to receive at least one subscription message for use in subscribing to one or more specific data objects stored in the data repository of the decentralized revision control system.
 4. The system of claim 3 wherein the data provisioning component is further operative to determine whether certain characteristics of the specific data objects stored in the data repository of the decentralized revision control system have changed.
 5. The system of claim 4 wherein the data provisioning component is further operative, in the event it is determined that certain characteristics of the specific data objects stored in the data repository of the decentralized revision control system have changed, to generate a notification of changes to the specific data objects stored in the data repository of the decentralized revision control system.
 6. The system of claim 1 wherein the configuration data in the data repository of the decentralized revision control system are stored as one or more data objects, and wherein the system further comprises: one or more application program components, at least one of the application program components being operative to register, with the data provisioning component, at least one application entity that requires access to the data objects stored in the data repository of the decentralized revision control system.
 7. The system of claim 1 wherein the decentralized revision control system is implemented using the Git revision control system.
 8. A method of provisioning data storage and runtime configuration in a telecommunications system or device, comprising the steps of: storing at least configuration data for the telecommunications system or device in a data repository of a decentralized revision control system; receiving, at a data provisioning component, at least one request for access to, or manipulation of, the configuration data stored in the data repository of the decentralized revision control system; and sending, by the data provisioning component, at least one command to the decentralized revision control system to implement the requested access to, or manipulation of, the configuration data stored in the data repository of the decentralized revision control system.
 9. The method of claim 8 wherein the storing of the configuration data in the data repository of the decentralized revision control system comprises storing the configuration data in the data repository of the decentralized revision control system as one or more data objects, and wherein the method further comprises: receiving, at the data provisioning component, at least one subscription message for use in subscribing to one or more specific data objects stored in the data repository of the decentralized revision control system.
 10. The method of claim 9 further comprising: determining, by the data provisioning component, whether certain characteristics of the specific data objects stored in the data repository of the decentralized revision control system have changed.
 11. The method of claim 10 further comprising: in the event it is determined that certain characteristics of the specific data objects stored in the data repository of the decentralized revision control system have changed, generating, by the data provisioning component, a notification of changes to the specific data objects stored in the data repository of the decentralized revision control system.
 12. The method of claim 8 wherein the storing of the configuration data in the data repository of the decentralized revision control system comprises storing the configuration data in the data repository of the decentralized revision control system as one or more data objects, and wherein the method further comprises: registering, by one or more application program components with the data provisioning component, at least one application entity that requires access to the data objects stored in the data repository of the decentralized revision control system.
 13. The method of claim 8 further comprising: implementing the decentralized revision control system using the Git revision control system.
 14. A system for provisioning data storage and runtime configuration in telecommunications systems or devices, comprising: a first decentralized revision control system including a first data repository, the first data repository being operative to store at least first configuration data for a first telecommunications system or device; a first data provisioning component communicably connected to the first decentralized revision control system; at least one second decentralized revision control system including at least one second data repository, the second data repository being operative to store at least second configuration data for at least one second telecommunications system or device, the second decentralized revision control system being communicably connectable to the first decentralized revision control system, the second configuration data including at least a portion of the first configuration data; and at least one second data provisioning component communicably connected to the second decentralized revision control system, the second data provisioning component being communicably connectable to the first data provisioning component, wherein, in the event certain characteristics of the first configuration data stored in the first data repository of the first decentralized revision control system have changed, the first data provisioning component and the second data provisioning component are operative to send one or more commands to the first decentralized revision control system and the second decentralized revision control system, respectively, thereby causing the first and second decentralized revision control systems to synchronize changes to the first configuration data stored in the first data repository of the first decentralized revision control system with the portion of the first configuration data stored in the second data repository of the second decentralized revision control system.
 15. The system of claim 14 wherein the first data provisioning component is further operative to determine whether the certain characteristics of the first configuration data have changed, and, in the event it is determined that the certain characteristics of the first configuration data have changed, to send a notification of changes to the certain characteristics of the first configuration data to the second data provisioning component.
 16. The system of claim 14 wherein the first decentralized revision control system and the second decentralized revision control system are each implemented using the Git revision control system.
 17. A method of provisioning data storage and runtime configuration in telecommunications systems or devices, comprising the steps of: storing at least first configuration data for a first telecommunications system or device in a first data repository of a first decentralized revision control system; storing at least second configuration data for at least one second telecommunications system or device in at least one second data repository of at least one second decentralized revision control system, the second configuration data including at least a portion of the first configuration data; in the event certain characteristics of the first configuration data stored in the first data repository of the first decentralized revision control system have changed, sending one or more commands by the first data provisioning component and the second data provisioning component to the first decentralized revision control system and the second decentralized revision control system, respectively; and in response to the sending of the one or more commands to the first and second decentralized revision control systems, synchronizing, by the first and second decentralized revision control systems, changes to the first configuration data stored in the first data repository of the first decentralized revision control system with the portion of the first configuration data stored in the second data repository of the second decentralized revision control system.
 18. The method of claim 17 further comprising: determining, by the first data provisioning component, whether the certain characteristics of the first configuration data have changed; and in the event it is determined that the certain characteristics of the first configuration data have changed, sending, by the first data provisioning component, a notification of changes to the certain characteristics of the first configuration data to the second data provisioning component.
 19. The method of claim 17 further comprising: implementing each of the first decentralized revision control system and the second decentralized revision control system using the Git revision control system. 